Other techie stuff
¬
 
Mac and NeXT systems do not use identical type family names.  For instance, what the Mac calls `Times', the NeXT calls `Times-Roman'.  Convert RTF does it's best to convert between these.  Strangely, the  NeXT system can generate a name in the rtf font table like `NewCenturySchlbk-BoldItalic'.  This is strange because it's listing a stylistic variation instead of a family name.  This application does NOT deal with these properly.  It gets converted to just `New Century Schlbk'.  This may cause initial New century schoolbook text to be roman instead of bold italic.

Some Mac applications (e.g. Word) sometimes use fonts in their documents, but don't list them in the rtf font table (usually this is when the fonts in question were not installed on the Mac when the file was saved as an RTF file).  If Convert RTF finds a font reference like this, it will create a new entry in the font table, and name it UnnamedFont#, where # is the number of the font in the file. This is useful to know only if you are examining the output from Convert RTF.

When converting an RTF file, two other cleanup tasks are done: If there is a color table in the document, but it is not used, then it will be completely removed.  Also, unused entries in the font table are removed (Microsoft Word tends to write out every single bloody type family name installed in the system, even if you only use Courier).  In some circumstances, this can produce a document without a font table.  This doesn't seem to hurt anything.

Standardly, rtf `source code' seems to be written out so it is as dense as possible with many instructions on a single line.  This application writes out rtf in what I consider to be slightly prettier format.  You may hate it, though, for all I know.  The basic algorithm is: one control word on a line, unless it is one of a small number of tokens that all fit in a single group (between {}) .  Many words (things that are not control symbols, control words, begin, or end groups), however, can be written on one line.  This uses more bytes in storage, but I think makes the document far more readable (though, an occasional thing like NeXT's bizarre graphics inclusion statement come out looking strange)